Autogenerated HTML docs for v1.5.6.1-156-ge903b
diff --git a/git-archimport.txt b/git-archimport.txt index 603117c..f089deb 100644 --- a/git-archimport.txt +++ b/git-archimport.txt
@@ -9,7 +9,7 @@ SYNOPSIS -------- [verse] -'git-archimport' [-h] [-v] [-o] [-a] [-f] [-T] [-D depth] [-t tempdir] +'git archimport' [-h] [-v] [-o] [-a] [-f] [-T] [-D depth] [-t tempdir] <archive/branch>[:<git-branch>] ... DESCRIPTION @@ -34,12 +34,12 @@ Make sure you have a recent version of `tla` available in the path. `tla` must know about the repositories you pass to `git-archimport`. -For the initial import `git-archimport` expects to find itself in an empty +For the initial import, `git-archimport` expects to find itself in an empty directory. To follow the development of a project that uses Arch, rerun `git-archimport` with the same parameters as the initial import to perform incremental imports. -While git-archimport will try to create sensible branch names for the +While `git-archimport` will try to create sensible branch names for the archives that it imports, it is also possible to specify git branch names manually. To do so, write a git branch name after each <archive/branch> parameter, separated by a colon. This way, you can shorten the Arch @@ -84,7 +84,7 @@ -o:: Use this for compatibility with old-style branch names used by - earlier versions of git-archimport. Old-style branch names + earlier versions of `git-archimport`. Old-style branch names were category--branch, whereas new-style branch names are archive,category--branch--version. In both cases, names given on the command-line will override the automatically-generated
